home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Windows Expert
/
Windows Expert.iso
/
network
/
winntnet.zip
/
WINNTNET.POL
< prev
Wrap
Text File
|
1993-02-13
|
20KB
|
525 lines
W I N * N T * N E T
Policy Document
Version 1.00
November 15, 1992
0 Contents
0 Contents
1 Overview
1.1 Purpose
1.2 Definitions
1.2.1 WIN*NT*NET Member(s)
1.2.2 Hatching Hub(s)
1.2.3 Windows NT Related File(s)
1.2.4 Downlink
1.2.5 Uplink
1.3 How Do We Operate?
1.3.1 WIN*NT*NET Topology
2 Memberships
2.1 Requirements to be a WIN*NT*NET Member
2.1.1 Familiarity with Policy
2.1.2 Equipment
2.1.3 Echoes
2.1.4 Costs
2.1.5 Polling
2.1.6 Files
2.2 Joining WIN*NT*NET (The Process)
2.2.1 Find a Feed
2.2.2 Request
2.2.3 Setting Up
2.2.4 Announcement
2.3 Leaving WIN*NT*NET
3 Hatching Hubs
3.0 Overview
3.1 Becoming a Hatching Hub
4 Files
4.0 Overview
4.0.1 New Files
4.0.2 File Checking
4.0.3 File Announcement
4.0.4 Time Lag
4.1 Distribution and Hatching
4.2 Files Requirements
4.3 Files Availability
4.4 Important Files related to WIN*NT*NET
4.4.1 WIN*NT*NET.ZIP
4.4.2 INFO$$??.ZIP
5 Conflicts and Problems
6 Future of WIN*NT*NET
6.1 FILE_REQ
6.2 FileBone
7 Contacting WIN*NT*NET
7.1 Snail Mail
7.2 Electronic Mail
7.3 Direct Call
8 Appendices
8.1 New Echoes
8.1.1 Echo Nametags
8.1.1.1 File Echoes
8.1.1.2 Message Echoes
8.2 Examples for Setup Configuration
1 Overview
1.1 Purpose
The goal of WIN*NT*NET is to provide a free, fast and efficient way to
distribute Windows NT related files. The scope of the software that
distribute within WIN*NT*NET are mainly Microsoft Win32, Win32s, and
Windows NT Operating System related. There is no cost for ANY WIN*NT*NET
member to access the files distributed, except telephone fees if toll
calls are needed to get the files.
WIN*NT*NET is not affiliated with Microsoft Corporation.
Note *** For those who are looking for Windows 3.x software:
This network is not intended for distributing Microsoft Windows 3.x
and Win16 software. And please notice the difference between
Windows 3.x/Win16 and Windows NT/Win32/Win32s. Although Windows NT is
capable to run Windows 3.x and Win16 programs, WIN*NT*NET will NOT
distribute Windows 3.x and Win16 software. ***
1.2 Definitions
1.2.1 WIN*NT*NET Member(s)
System that meets the requirements set forth in the latest WIN*NT*NET.POL
policy file to be a member of WIN*NT*NET.
1.2.2 Hatching Hub(s)
Pre-assigned WIN*NT*NET members who has the authority to hatch files into
WIN*NT*NET. Refer to Section 3 for more information about Hatching Hubs.
1.2.3 Windows NT Related File(s)
Win32 applications, Win32s applications, information files about Windows
NT, plus any file that could be associated with Windows NT and NT
applications.
1.2.4 Downlink
System that receives file(s) from other systems.
1.2.5 Uplink
System that sends file(s) to other system.
1.3 How Do We Operate?
Unlike most of the other File Distribution Networks (FDN), the
administration of WIN*NT*NET does not put a lot of restrictions on
WIN*NT*NET members; so that the network is easier for expanding and future
growth. System interested to join WIN*NT*NET can be able to become a
member system in a short amount of time.
1.3.1 WIN*NT*NET Topology
Files flow from Uplink to Downlink.
Uplink should never receive files from Downlink members.
Note: Hatching Hubs are always the uplink of other
non-hatching hubs because hubs should never receive
files from non-hatching hubs in file echoes.
[more]
|
HUB1
/ \
/ \ * Hubs are closely connected
/ \ to ensure the integrity of
/ \ the files being distributed.
[more]-HUB2 HUB3-[more]
| | * Node 1 and Node 2 are the
| | downlink of Hub 1 and Hub 2
NODE1 NODE2 respectively.
| / \
| / \ * Node 3 is the downlink of Node
NODE3 / \ 1 while Node 4 and Node 5 are
NODE4 NODE5 the downlinks of Node 2.
2 Memberships
2.1 Requirements to be a WIN*NT*NET Member
2.1.1 Familiarity with Policy
New nodes should familiarize themselves with policy before requesting
membership.
2.1.2 Equipment
The member should run a, but not limited to, Fidonet-compatible BBS
system.
2.1.3 Echoes
Among all the message echoes and file echoes, only message echo
WINNTADM and file echo NT_ADM must be carried by every member. In
other words, a system carries WINNTADM and NT_ADM is enough to be
identified as a WIN*NT*NET member. We don't want every member to carry
every single echo available on WIN*NT*NET like other FDNs do to ensure the
flexibility.
2.1.4 Costs
WIN*NT*NET member should be aware that long-distance calls may
be necessary to obtain the files, if no local links are available.
If calling is restricted to late night rates, long distance bills should
not be added significantly.
2.1.5 Polling
WIN*NT*NET member is recommended to poll his uplink once a week.
Any member who does not pick up WIN*NT*NET traffic for a period
exceeding 30 days, and not making suitable alternate arrangements
with its uplink, shall be disconnected from uplink. It is also
recommended that member who has downlink should poll more
frequently to make sure the files are moving at a reasonable pace
across systems.
2.1.6 Files
WIN*NT*NET member should make WIN*NT*NET.ZIP (which consists of
WIN*NT*NET.POL and WIN*NT*NET.INF) available for users to download or
file requestable using the magic filename "WIN*NT*NET". See Section 4.4.1
for more information on file WIN*NT*NET.ZIP.
2.2 Joining WIN*NT*NET (The Process)
2.2.1 Find a Feed
After reading this Policy Document, look at the file WIN*NT*NET.INF
which should come with this file. Locate a system under
'List of WIN*NT*NET members' as your uplink.
2.2.2 Request
Net mail your uplink saying that you are interested to join WIN*NT*NET.
Also tell your uplink what message echoes and file echoes you want to
pick up. For lists of both message and file echoes, please refer to
WIN*NT*NET.INF. Note that the message echo WINNTADM and file echo
NT_ADM must be picked up by every WIN*NT*NET member.
2.2.3 Setting Up
Your uplink should take care the rest of technical work to set you up
while you setup your system ready to receive messages and files.
Normally, you have to call your uplink to pick up the traffic instead
of your uplink calls you unless you and your uplink have made a
special arrangement.
2.2.4 Announcement
After the link is established, please post a message in WINNTADM
saying that you are now joining WIN*NT*NET. This is required because
we use these postings to keep track who have joined WIN*NT*NET;
and hence put your system in the 'List of WIN*NT*NET members' at
the next release of information package.
2.3 Leaving WIN*NT*NET
When a member leaves WIN*NT*NET, one of the following procedures
should be taken place:
. Prior to leave WIN*NT*NET, the member should post a message in
WINNTADM saying that he/she is now leaving WIN*NT*NET, OR
. The uplink of the leaving member posts a message in WINNTADM
saying that such member has left WIN*NT*NET.
This is necessary for us in order to keep an update 'List of WIN*NT*NET
members' that appears in every month's information package.
3 Hatching Hubs
3.0 Overview
Hatching hubs are pre-assigned WIN*NT*NET members who have the
authority to hatch files into WIN*NT*NET. To gain such authority, the
system must have a steady source for new Windows NT related files which
is not currently available on WIN*NT*NET. To ensure the consistency of the
files distributions, we hope to keep the number of hatching hubs as few
as possible to prevent potential dupe files.
3.1 Become a Hatching Hub
For more information about becoming a hatching hubs for WIN*NT*NET,
please contact Chelsea Carlstedt @:
Fidonet: 1:100/375
Internet: Ucheswic@toadnet.org,
Compuserve: 71553,1075
4 Files
4.0 Overview
The following sections describe the basic "flow" of the files on
WIN*NT*NET:
4.0.1 New Files
Anyone, either WIN*NT*NET member or non member, finds a new Windows NT
related file that he/she wants to hatch into WIN*NT*NET should send this
file to one of the WIN*NT*NET hatching hubs which listed in WIN*NT*NET.INF
for distribution.
4.0.2 File Checking
The hatching hub who receives this new file would look at the
current WIN*NT*NET file base to see if such a file exists. If such file
exists, then it should be checked to see if the newly received file
is a newer version than the existing one. If it is not a newer
version, then this file will not be hatched and a notification
should be made to the original sender about why such file is not
hatched. Otherwise, this hatching hub would hatch the file if no
other hatching hubs have the same file after asking them. If more
than one hatching hub has the same new file, only ONE hatching hub
will hatch the file.
4.0.3 File Announcement
This hatched file should be put on hold on this hatching hub and
waiting for others to pick it up. When it arrives the headquarters
of WIN*NT*NET, Windows NT Network, Fidonet 1:100/375, a file
announcement for this file will be generated and posted in message
echo WINNTFA. A file announcement should be only made from WIN*NT*NET
headquarters to ensure the accuracy and consistency.
4.0.4 Time Lag
It takes about 2 to 3 weeks for a newly hatched file to reach all
WIN*NT*NET members.
4.1 Distribution and Hatching
To ensure consistency across the system, ONLY hatching hubs have the
authority to hatch files. A "List of WIN*NT*NET Hatching Hubs" is always
available updated in file WIN*NT*NET.INF.
Non-hatching hubs members should never directly hatch
files into WIN*NT*NET under any circumstance. NOTE: Any non-hatching
hubs member violates this rule may result in immediate losing the
status of being a WIN*NT*NET member. The reason for not letting non-
hatching hubs members to have the authority hatching files is
understandable. Files would be easily duplicated if every member
wants to hatch files into WIN*NT*NET without pre-arrangement. Hatching
hubs are working very closely together to ensure no files are
duplicated.
Instead of hatching files directly into WIN*NT*NET, non-hatching hubs
should follow one of these procedures to distribute the files:
1) by direct mail addressed to:
WIN*NT*NET
234 Couch Avenue
St. Louis, MO 63122 USA
2) by file-attach, accompanied by a net message sending to any ONE of
the hatching hubs listed in file WIN*NT*NET.INF with:
a) a short description of the file
b) a summary of how it was obtained by the person sending it
(i.e., directly from the author, from CompuServe, etc.)
These files will be put on "hold" for pickup by direct feeds.
Files will be hatched in ".TIC" format.
If you are interested to become a hatching hub, see Section 3.1.
4.2 Files Requirements
Please test everything you want to distribute on WIN*NT*NET. If it is
an application or program that suppose to run under Windows NT, test it
on your machine first, and make sure that it works as intended, before
sending it to hatching hubs.
4.3 Files Availability
Obtaining the complete WIN*NT*NET files collections may be done in several
ways.
Mail sufficient FORMATTED 1.2 MB, 1.44 MB, 720 K or 360 K diskettes
along with $5 for RETURN airmail postage to:
Windows NT Network
234 Couch Avenue
St. Louis, MO 63122 USA
If you prefer, Windows NT Network can provide the files on
generic diskettes any format. Prices are as follows:
1.44 MB $22.00 including postage
1.2 MB $22.00 including postage
720 K $24.00 including postage
360 K $24.00 including postage
As an alternative, Windows NT Network BBS (314)965-5296 always
has the whole collection of WIN*NT*NET files online. They are all
available for File Request or download online. File Request using magic
name "FILES" would get you a complete listing of the WIN*NT*NET
Collections. The Windows NT Network BBS is Cheswick's International:
@1:100/375 (314)965-5296 HST DS or (314)965-1385 14.4 v.32b
4.4 Important Files related to WIN*NT*NET
The following files are the information and administration files for
WIN*NT*NET that come down from file echo NT_ADM periodically:
4.4.1 WIN*NT*NET.ZIP
WIN*NT*NET.ZIP (Hatch through NT_ADM whenever a new version of Policy
Document is released) consists of the following files:
. HISTORY.DOC: History of WIN*NT*NET Policy
. README.DOC: Information about this file
. WIN*NT*NET.POL: WIN*NT*NET Policy Document
. WIN*NT*NET.INF: List of WIN*NT*NET File Echoes
List of WIN*NT*NET Message Echoes
List of WIN*NT*NET Members
List of WIN*NT*NET Hatching Hubs
4.4.2 INFO$$??.ZIP
INFO$$??.ZIP (Hatch through NT_ADM monthly) where $$ is the year and ??
is the month. For example, INFO9209.ZIP would be the WIN*NT*NET
information file for September 1992. This file consists of the following
file:
. README.DOC: Information about this file
. WIN*NT*NET.FIL: List of all files that have been hatched into WIN*NT*NET
up to that time
. WIN*NT*NET.INF: List of WIN*NT*NET File Echoes
List of WIN*NT*NET Message Echoes
List of WIN*NT*NET Members
List of WIN*NT*NET Hatching Hubs
5 Conflicts and Problems
If there are any conflicts and problems between the uplink and the
downlink that cannot be resolved, either party could send a netmail
to WIN*NT*NET headquarters, Windows NT Network, which addresses are
listed at the bottom of this file. By no means we want to get into
too much politics, but just in case anyone has problem with his/her
downlink or uplink, one can always ask for help from WIN*NT*NET
headquarters.
6 Futures of WIN*NT*NET
6.1 FILE_REQ
Access to message echo FILE_REQ which is a Fidonet Zone 1 backbone
conference for posting file announcements. So that everyone would know
what new files are coming out from WIN*NT*NET.
6.2 FileBone
WIN*NT*NET is now available on the FileBone.
The FileBone is functional equivalent to what Fidonet backbone does
to message conference.
7 Contacting WIN*NT*NET
7.1 Snail Mail
Windows NT Network
234 Couch Avenue
St. Louis, MO 63122 USA
7.2 Electronic Mail
CompuServe: 71553,1075
Fidonet : WIN*NT*NET @ 1:100/375
Internet : Ucheswic@cheswicks.toadnet.org
Chelsea Carlstedt@f375.n100.z1.fidonet.org
7.3 Direct Call
Voice : (314)965-7590
Fax : (314)965-1783
BBS/Data : (314)965-5296
BBS/Data : (314)965-1385
8 Appendices
8.1 New Echoes
Suggestions for possible new areas are always welcomed. Proposal should
be posted in WINNTADM. Please refer 8.1.1 for suggested naming methods
of the echoes. If responses for such possibly new area are reasonably
good, then this area is created. It will first made available on
hatching hubs and other members could then join in the new area.
8.1.1 Echo Nametags
Please consider the following naming conventions, but not limited to,
to ensure the consistency of the echo nametags.
8.1.1.1 File Echoes
Use NT_* for file echoes while * is your choice.
8.1.1.2 Message Echoes
Use WINNT* for message echoes while * is your choice.
8.2 Examples for Setup Configuration
Here are some examples to setup program TICK which is used for
controlling file echoes:
A typical entry for a file echo in TIC.CFG would be something like:
AREA c:\WINNTNET\ntadmin NT_ADM
1:123/456 PASSWORD * &
This is saying that your system will have a file echo area named NT_ADM,
and files in this echo are saved in C:\WIN*NT*NET\Ntadmin directory. Your
link for this area is 1:123/456 and the password between your system and
1:123/456's system on this echo is set to "PASSWORD". "* &" means that
your system will accept files from 1:123/456 but will NOT echo files to
it. In other words, 1:123/456 is your uplink.
If someone wants to be your downlink and asks you to feed him/her files,
then you may add the following entry:
(Assume this request system's node number is 1:456/789)
AREA c:\WINNTNET\ntadmin NT_ADM
1:123/456 PASSWORD * &
1:456/789 HELLO H
Now, 1:456/789 is participating in NT_ADM echo. The password between
your system and 1:456/789's system for this echo is HELLO. Note that
the same password must be set up in both system's setup in order to get
things working. "H" means that your system will send files to 1:456/789
and hold the files for it but your system will not accept files from it.
This conforms the rule set out in section 1.3.1 that uplink members
should never receive files from downlink members.
The function REPLACE is recommended to use in TICK because updated files
are distributed occasionally.
Please refer to the TICK's manual for more information about how to set
things up, it should be easy and straight forward. If you have any
question about setting file echoes up, ask for help in WINNTADM
conference.